home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-06-26 | 2.2 KB | 50 lines | [TEXT/GEOL] |
- Item forwarded by BURBECK.S to LICHTY BERNS1
-
- Item 3900905 7-June-89 10:10
-
- From: ATTACHMATE Attachmate, John Bartleson, PRT
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: TObject.Compare Retraction
-
- Hello:
-
- On reflection, my previous link in which I argued against adding a compare
- methiod to TObject was wrong for the following reasons:
-
- 1. The overhead for adding a new method to TObject (assuming it does not
- require any new fields) is negligible. If no subclasses override the method
- then the overhead is one jump table entry. If the method is never called, then
- this entry is removed for optimized code. If I were making a subclass with
- this functionality, I would require this amount of overhead anyway.
-
- 2. On first reflection, I thought that many objects never need to be sorted.
- But in reality, almost every object except for TApplication appears in a list
- somewhere. Why not make these lists fast. Besides, making generic collection
- classes requires some support from each object in them. I think fast, generic
- collection classes are good.
-
- 3. I believe that my apprehension concerning TObject becoming muddled with
- lots of useless methods is in part due to the lack of documentation in MacApp
- 2.0ß5. There are already some undocumented methods in various MacApp objects.
- Ideally, I would have an on-line documentation browser so that I can look at
- the definition of TObject when I get confused concerning what Compare is
- supposed to do. Right now, I have to browse the SOURCE with the MADA browser
- DA. While the browser DA is real handy, it is only a temporary solution to the
- real need for having well-organized, on-line documentation for MacApp objects.
-
- 4. A rich, well-thought out set of methods for the root object in an
- object-oriented system has been shown to be an advantage in Smalltalk and other
- OOPS. Since Object Pascal has no multiple-inheritence and little built-in
- run-time flexibility in terms of making objects into other objects, a rich set
- of methods for TObject is even more important.
-
- Anyway, I thought I would SELF.Correct before I get too buried by OOP gurus
- pointing me along the correct road to TNirvana.
-
- John D. Rinaldo, Jr.
- Attachmate Corporation
-
-
-